feat(privacy): fixed MeshView-specific notice, replaces configurable text model - #14

The previous commit trimmed one section out of a config-driven page. That
missed the requirement: the notice is an approved document, and the page's
visible content must be exactly that document -- no more, no less.

The page is now a FIXED document. public/privacy.js carries the notice as a
typed block/run structure (heading, paragraph, list, bold, link, hard break)
and renders it through a closed set of tags. Config decides only WHETHER the
page is published, never what it says: privacy.js reads cfg.enabled and
nothing else, so no operator value -- current, stale or newly added -- can
add, remove or reword a line.

Removed from the rendered page (static boilerplate that was never in the
approved text): the "Privacy Notice" title, effective date, data-controller
and privacy-contact header, the CoreScope intro paragraph, "What data this
site processes", the legal-basis label and its "stated by the operator"
note, "Sources of the data", "Who can receive the data", the retention
caveat, "Channel and direct messages", "Storage in your browser", "Server
and proxy logs", "External services", "International transfers", "Hidden
nodes", "Automated decision-making", "Changes to this notice" and the DPO
block.

Config fields removed, because the page no longer reads any of them and a
required field that cannot affect the page is a trap -- a blank one would
have withheld the notice entirely:

  PrivacyConfig  -> Enabled only. Gone: controllerName, contactEmail,
  effectiveDate, purposesText, legalBasisType, legalBasisText,
  legitimateInterestsText, retentionText, recipientsText, dataSourcesText,
  thirdPartyServicesText, internationalTransfersText, browserStorageText,
  serverLogsText, automatedDecisionMakingText, dpoName, dpoContact.

  PrivacyClientConfig -> Enabled only; hiddenNamePrefixes no longer rides
  along in the privacy block.

With no fields left to check, Validate(), logPrivacyConfigErrors(),
privacyEmailRe, privacyLegalBasisTypes and PrivacyLegalBasisTypes() are gone
too, and with them the regexp/sort/strconv imports. The publish gate is now
just privacy.enabled. Config.ActiveHiddenNamePrefixes() is KEPT: the privacy
page no longer consumes it, but its test pins an IsNameHidden invariant that
belongs to node hiding.

Safety: the notice is code, not config. Every text run goes through
escapeHtml; the single href is a compile-time constant re-checked against an
absolute-http(s) pattern at render time, and an unsafe URL degrades to plain
text instead of becoming a link. Nothing from window.MC_PRIVACY reaches the
DOM. A pre-removal config.json still parses and is still accepted -- its
values are simply ignored and never published.

Tests: a golden test normalises the rendered markup back to visible text and
compares the whole result against the authoritative Markdown, held verbatim
in the test (String.raw, so JS cannot eat the \. \@ escapes or the
hard-break backslash before the comparison sees them). Mutation-checked: it
fails on added text, removed text and a single reworded word. Alongside it:
exactly 7 headings in order, exactly 4 data points with their bold lead-ins,
the MeshCore URL, meshview.dk and kontakt@meshview.dk rendering without
backslashes, both square-bracket passages intact, and no extra section.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…mment

The comment still described the field as "operator-configured
privacy-notice content" published only once the block passes
PrivacyConfig.Validate(). Neither is true any more: the notice is a fixed
document in public/privacy.js, Validate() no longer exists, and the block is
published on privacy.enabled alone.

Comment only — no code, no behaviour change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Independent review compared the rendered #/privacy notice word-for-word
against the user's authoritative text (supplied directly, not sourced from
this repo). Every heading, paragraph, list item, bold emphasis, line break
and bracketed passage matched exactly except one: the MeshCore link pointed
at https://meshcore.co.uk/, where the approved text specifies
https://meshcore.io.

Three call sites carried the old URL and are now aligned:
- public/privacy.js: the DOC link itself (the rendered href)
- test-privacy-page.js: the AUTHORITATIVE golden fixture
- test-privacy-page.js: the link-safety assertion and the
  "notice text lives in code" static-source check

No other content changed. Structure (7 headings, 4 list items, 1 link),
bold segments, the controller/contact line break, and both bracketed
passages were independently re-verified unchanged and byte-identical to
the approved text after this fix.

test-privacy-page.js: 34/34 passing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>